-
Notifications
You must be signed in to change notification settings - Fork 25
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Implement currying interface, resolve #18 #19
Conversation
The question is, should we possible have just one interface? |
It would make the lib code simpler and users code more unified, less confusion. |
I did the exact same thing for react-jss some time ago. |
I agree, looks like it's better to make this breaking change now |
And I can't get real pros for the previous API |
fontSize: 12, | ||
color: (props) => props.theme.textColor | ||
}) | ||
|
||
// You can also use curried interface this way. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
its all curried ...
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
but yeah a separate example is still good.
btw. don't forget to add changelog with breaking change notice and release a new major verison |
BREAKING CHANGE: keep just only curried interface